Software Vault: The Diamond Collection/The Diamond Collection (Software Vault)(Digital Impact).ISO/cdr14/autpub52.zip/INCENTIV.TXT

Text File | 1992-11-01 | 15KB | 347 lines

This list of possible registration incentives is published unofficially by
the ASP as a service to its Author Members. It is not an "official" list
but these specific ideas have been reviewed by the Author Membership
Committee, Author Compliance Committee, and the Board of Directors and are
in keeping with the ASP's Policy on No Crippling.

Thanks go to Bob Schenot, Paul Munoz-Colman, and Bob Ostrander for this
compilation.

First, a couple of short explanations. The Policy on No Crippling is ASP's
requirement that

   1) Shareware and registered versions must be essential the same (with
      some exceptions.
   2) Programs must be fully documented. (note that the documentation
      doesn't have to be identical between shareware and registered
      versions, just that all the features of the shareware version
      must be explained)
   3) Solicitation of non-shareware versions (NSV), other than the
      registered version, have some restrictions.

Please see the Policy of No Crippling statement available on ASP's
CompuServe forum, library 4 as REQUIRE.TXT or from the Executive Director
on the New Author disk (616-788-5131).


Additional Similar Programs
   Notably used with games and educational software where "more of the
   same" are often wanted by customers.
   Ex: Additional similar games
          7-card stud as a bonus for a 5-card stud game
          More "levels" of game in separate editions
       Alphabet learning system offered to registrants of Number learning
          system
       Typing tutor for Dvorak keyboard offered in addition to QWERTY
          layout
       Additional flashcards or languages
   NB: Additional pictures, fonts, icons, etc. are normally only
          acceptable when the collection offered is of such substantial
          size will deter distribution by BBS (ie is large enough that
          the download time will give pause to the customer)

Branding the User's name on the product
   Often psychological, this can be used to help prevent the spread of
   registered versions.
   Ex: Sign-on says "non-registered" in shareware version with a facility
          to put the user's name on the registered version.

   (See Customization and Watermarks)

Bug Notices
   If a customer is going to rely on a program for financial gain they
   want to know of any problems ASAP.
   (See Newsletters and Update Notices)

Cheat Codes
   "Cheat Codes" for games have been specifically approved by the ASP
   BoD as registration incentives. These are somewhat akin to hint books.

Commissions
   Paying registered users who promote other registrations can build
   customer loyalty and help spread your product. The downside is that
   the administration of commissions is unwieldy.

Contests
   Holding a contest for the best ..whatever.. can build good customer
   relations. The prizes can be as small as an acknowledgement in a future
   version.
   Ex: Best game design
       Best database design
       Most imaginative use

Current Version
   Obvious but sometimes overlooked. A disk with the current version is
   normal but not mandatory. Don't forget to ask what disk format the
   customer needs.

Customization
   Adding user-specific data to the screens, printouts, etc. Also offering
   to customize to the user's specifications can generate lucrative
   contract work.
   Ex: Child's game with a specific welcome-in.
   (See Branding and Watermarks)

Data Conversion Programs (others' formats)
   Additional programs to convert data to or from competing or
   complementary programs.
   Ex: Word Processor addition to convert files from Word Perfect format
       Graphics programs addition to convert .PCX files to proprietary
          format
       Graphics programs addition to convert LaserJet fonts to internal
          format
       Payroll addition to convert files to Quicken format
       Genealogy addition to convert files to Gedcom format
   NB: Of course if the basic function of the system is to do data
          conversion this incentive doesn't apply

Data Conversion Programs (your old formats)
   New versions of a program that use a different file format are not
   usable by people who have built up a database with an older version.
   Offering a data conversion program to registrants enables these people
   to continue using your program (and has the side effect of encouraging
   people to register rather than key in their data all over again).

   This combined with an old-age warning can be a powerful registration
   incentive.
   (See Old-age Warning)

Discount Offers
   Discounts on your other programs, other peoples programs (by
   arrangement), and some standing offers for ASP members.
   Ex: Shareware Magazine, CompuServe discounts.
       Discount on a Thesaurus with a Word Processor.

Discounts on Registrations
   Discounts for certain classes of registrants can be effective. Often
   psychological.
   Also discounts if the registrant supplies usage tips, "icons and the
   like" (see below), or as a reward for telling you where they got the
   shareware version have not only an incentive to register but also can
   give you valuable information.
   Ex: Discounts for User Group members, Senior Citizens, Students,
          Teachers, etc.
       Multiple-unit discounts and site licenses
       Discounts for on-line registration via your BBS
       Some authors offer "poverty discounts" that merely put off the
         actual registration. This has been seen to have both good and
         bad points.

Enhanced Versions
   Other versions can be offered via advertising a "Non-Shareware Version"
   in your documentation. See the "NSV" discussion in REQUIRE.TXT. These
   versions can have more features, less features, or different features.
   Ex: LAN-capable versions
       TSR versions
       Word Processor with spelling checker as NSV

Free Goodies
   On the theory that people will buy two packs of cigarettes to get a
   free pen, all sorts of freebies can be offered. They don't really have
   to be related. Some sample pre-printed forms can lead to more sales.
   Ex: A sky chart with an Astrology program
       A deck of cards with a Card game
       Note pads, pens, glasses, anti-glare screens, koala bears, or
          anything with your logo on it.
   (See Pre-printed Forms)

Guarantees
   Lifetime warranties and money-back guarantees are good PR and are very
   rarely used by customers (after all, they've had a chance to try it
   before they bought it).

Hint Books
   While this is normally associated with games, additional documentation
   to help the user get the most out of any system is suitable.
   Ex: Where the rubies are buried in the 3rd level maze
       How to best design a database with a DBMS
       Writers' guidebooks with a Word Processor

Honesty
   Reminders that shareware is based on trust can be effective by
   themselves. Many people do register just because it is the "right thing
   to do". These can range from "good vibes" reminders through humorous to
   downright sinister.
   Ex: "Shareware is based on trust. I trust you to pay for this program
          if you are using it."
       "Support your local programmer."

       Actually, the ASP does NOT recommend either of the following:

       "If you don't register this program the bald bat of the Balkans
          will lay its eggs in your power supply."
       "Continued use of this program is a violation of 17 United States
          Code, sections 101 through 810. This carries severe financial
          penalties including but not limited to fines of up to $50,000
          per violation."

Icons and the like
   Any program that has customizable anything can build a real following
   by offering these items and possibly a program to do the editing.
   Ex: Custom tiles for a MahJongg game
       Custom card backs for a Solitaire game
       Entertaining screens for screen blankers
       Additional fonts (both on-screen and printed)

License for Future Versions
   Your registration license can be structured so that it only applies to
   the version customers have or the version you send them. It can also
   apply until a specific future version (such as the next major X.xx
   update). Including a license to use future versions is not mandatory
   but many users expect a perpetual license.
   (See Updates (Discounted or Free))

Newsletters
   Regular communication with customers builds brand loyalty and enhances
   repeat sales and upgrade rates.
   (See Bug Notices and Update Notices)

Non-Essential Features
   Registered versions can have supplemental features which provide a
   convenience.
   Ex: Screen color changing module
       Built-in text editor in Menu system

Old-age Warnings
   Notices that a program is (for instance) over 2 years old and that a
   newer, more powerful version is probably available will entice customer
   contact when they get a program from an untended BBS or when they've
   been using a program for some time. These must be done in good taste
   to inform rather than annoy the user or they defeat the purpose.
   (See (Data Conversion Programs (your old formats))

Passwords
   If your program has password protection of any kind, the effective use
   of this passwording can be restricted to the registered version. To do
   this, you can include a short line (on the data entry screen that asks
   for the password) that tells the user the valid password (of course
   with a short note that this little bit of help isn't shown in the
   registered version).

Pre-printed Forms
   Pre-printed forms can produce nicer looking output (especially on dot
   matrix printers. Nebs and other business forms have kickback schemes.
   Both pin-fed and laser forms are suitable.
   Ex: Invoice forms
       Rolodex cards
       Checks
   (See Free Samples)

Printed Manuals
   Powerful incentive when offering a large, bound manual. The larger the
   better.

Quick Reference Cards
   Similar to printed manuals, quick reference cards, keyboard overlays,
   etc. can help customers use your software more effectively.

Registration Reminder Screens (elimination of)
   Shareware versions may have up to 2 RRSs per running. See REQUIRE.TXT
   for details.

   It is effective to have RRSs come up at random times, sometimes not
   appearing at all, other times appearing. Some people don't show RRSs
   until the program has been used a certain number of times.

Related Programs
   Non-essential accessories and tools that can aid the user. These can
   be from other programmers via licensing agreements. Shareware
   distribution versions of other programs can be sent to registrants.
   Ex: Stand-alone spelling or grammar checkers added to Word Processor
       Database browsers added to any program (several are available for
          .DBF file formats for instance)
       Formatted printers added to programming tools
       Teacher's Workbook with Educational programs

Sample Files
   Examples, templates, and sample data can aid the learning process. They
   can also be tied to tutorials. Often this material is best included in
   the shareware version so the potential customer can better evaluate the
   product.
   Ex: Franklin Roosevelt's family tree set up for a Genealogy system
          (his family tree is extremely interesting by the way)
       Extra pictures to color for a coloring book
       Pre-setup databases with a DBMS
   (See Tutorials)

Source Code
   Source for the product can be offered or sold for an additional price.

Subscription Data
   If the program requires data that needs to be kept up-to-date this is
   very effective. These can be offered via a pay BBS or through the mail.
   Ex: Zip code lists
       Postal/UPS rates
       Lottery results
       Baseball card databases
       Tax tables

Support
   A minimal level of customer support is required by the ASP. This is 3
   months of at least support by mail. Support by telephone, BBS, or
   CompuServe is also a good idea. Unlimited, or lifetime support is no
   harder to offer since most customer inquiries come in the first few
   days of use. If you cannot give support yourself, there are companies
   who can do this for you.

   Additionally, customer support is a good way to gather information
   about what your customers (and therefore other potential customers)
   want. It can give you valuable information for designing the next
   version.

   It's also worth noting that having a telephone number in the
   documentation sometimes gives the user enough confidence in you to
   register. Some people try to phone the author before registering just
   to make sure that the author is still around. Even an evening-only
   phone number is enough.

T-Shirts, etc.
   If you generate a real following people love to show you off. These can
   be sold or given away.
   Ex: T-Shirts with your logo
       Mouse pads with your logo
       Baseball caps with your logo

Tutorials
   Additional explanatory material can be a good incentive; especially
   for complicated systems that need to be taught to end users. These
   might be accompanied by sample databases.
   Ex: Teachers' workbooks with educational systems
       DOS tutorials with just about any system
   (See Sample Files)

Unrelated Programs
   Non-essential accessories and tools that can aid the user. These can
   be from other programmers via licensing agreements. Shareware
   distribution versions of other programs can be sent to registrants.
   Ex: Small utilities, screen blankers, text editors, etc.
       Obsolete software you happen to have sitting around doing nothing

Update Notices
   Customers like to have the latest version. Often a notice of an update
   will reach them months before they would see a new shareware version.
   Many people report excellent response rates! A good source of added
   revenue.
   (See Bug Notices and Newsletters)

Updates (Discounted or Free)
   If your license includes use of future versions customers might
   obtain them from a BBS or disk vendor or might get them directly
   from you. Promising low-cost updates as a registration incentive can
   give the customer a good feeling.

   Some people send free updates of minor versions (bug fixes, etc.) to
   registrants. If you have BBS support, these updates can be posted
   there.

Watermarks (elimination of)
   The shareware version shows "unregistered version" on the screen or on
   printouts. The registered version eliminates this or allows for the
   user to put a name or message there. Watermarks MUST be unobtrusive.
   Ex: Author's trademark at the bottom of printouts
       One-line "printed by unregistered Smudgiekeeper" at the bottom
          of reports
       Automatic "taglines" added to communications programs
   NB: Any watermark that covers or is background to other printed
          material is not acceptable